Improvement: Allow for CloudFormationManagedUploadInfrastructure stack to be deployed without a KMS key #1101
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ubleshooting; it doesn't like the self-signed certificates from json-schema.org Signed-off-by: Sam Platek <[email protected]>
Signed-off-by: Sam Platek <[email protected]>
Signed-off-by: Sam Platek <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Issue #801
Description of changes:
Allows a flag or env variable to be set that will cause the stack that is deployed (
CloudFormationManagedUploadInfrastructure) to not deploy a KMS key. If the KMS key is not used, SSE will be used for the bucket. The KMS key will still be deployed by default unless the flag/env var is used.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.